Medway Council
Tree preservation zone
There is a problem
- 91 entries must have dates in YYYY-MM-DD format
entity: 19128489
- reference
- G111-1991
- name
- tree-preservation-order
- tree-preservation-zone-type
- geometry
- MULTIPOLYGON (((0.543672 51.393602,0.543676 51.393592,0.543697 51.393583,0.543718 51.393586,0.543730 51.393601,0.543723 51.393613,0.543705 51.393619,0.543680 51.393614,0.543672 51.393602)),((0.543423 51.393465,0.543430 51.393452,0.543448 51.393446,0.543473 51.393451,0.543481 51.393463,0.543474 51.393476,0.543456 51.393482,0.543435 51.393479,0.543423 51.393465)),((0.543599 51.393353,0.543606 51.393340,0.543624 51.393334,0.543644 51.393337,0.543656 51.393348,0.543649 51.393364,0.543631 51.393370,0.543607 51.393365,0.543599 51.393353)),((0.543849 51.393436,0.543864 51.393420,0.543885 51.393418,0.543899 51.393423,0.543907 51.393438,0.543896 51.393450,0.543876 51.393454,0.543854 51.393446,0.543849 51.393436)))
- point
- POINT (0.543664 51.393464)
- notes
- entry-date
- 2026-05-09
- start-date
- end-date
How to fix this issue
Your dataset is missing the start-date column.
The Tree preservation zone guidance explains how to fix the issue:
start-date
The date that the tree preservation order came into force, written in YYYY-MM-DD format.
Example: 1984-03-28
How to improve Medway Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL